While testing TCP & UDP tests (coming soon), I tracked down a bug in the
authoremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Mon, 27 Feb 2006 15:14:11 +0000 (16:14 +0100)
committeremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Mon, 27 Feb 2006 15:14:11 +0000 (16:14 +0100)
commit975a49cb6ecf4ff78ca05695705a1f808b39ca88
tree396fb8778b8885b216bb6e01ce506637288359d2
parentd8a4248e024d6f46529fbcfc950d67052826d03f
While testing TCP & UDP tests (coming soon), I tracked down a bug in the
IP addressing scheme
used by xm-test: each machine running network tests is using the same IP
addresses, so two machines
in the same network can cross-pollinate/interfere with each other's tests.

This patch changes the IP addressing scheme to add some randomness. It's
gone through a couple of dozen
passes of xm-test, some on -bridge and some on -route, while xm-test was
running on another box on the same network.

Signed-off-by: Jim Dykman <dykman@us.ibm.com>
tools/xm-test/lib/XmTestLib/Network.py